Generating animation overlays in a communication session

ABSTRACT

Method of generating animation overlays starts with a processor causing a communication interface for a communication session to be displayed at client devices. The processor receives from a first client device an animation sending request and causes an animation sending interface to be displayed in the communication interface of the first client device. The animation sending interface comprises animation overlay icons. Each of the animation overlay icons comprise a first avatar associated with the first user. The processor receives from the first client device a selection of a first animation overlay icon and causes the first animation overlay corresponding to the first animation overlay icon to be displayed as an overlay on the communication interface of each of the plurality of client devices. The first animation overlay is an animation that includes the first avatar. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/457,395, filed Jun. 28, 2019, which is incorporated by referenceherein in its entirety.

BACKGROUND

The popularity of electronic messaging, particularly instant messaging,continues to grow. Users increasingly use customized avatars withinelectronic messages such as texts and emails reflecting a global demandto communicate more visually.

These customized avatars can be personalized by the users to representthe users in various applications, video games, messaging services, etc.Since the customized avatars can be generated in a different array ofsituations, displaying various emotions, or even be animated, the usersare able to communicate their feelings more accurately in messages usingthe customized avatars.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. Some embodiments are illustrated by way of example, and notlimitation, in the figures of the accompanying drawings in which:

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network.

FIG. 2 is block diagram illustrating further details regarding amessaging system, according to exemplary embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored inthe database of the messaging server system, according to variousexemplary embodiments.

FIG. 4 is an exemplary flow diagram of a process according to variousaspects of the disclosure.

FIGS. 5A-5F are exemplary user interfaces according to various aspectsof the disclosure.

FIG. 6 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described.

FIG. 7 is a block diagram illustrating components of a machine,according to some exemplary embodiments, able to read instructions froma machine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

Among other things, embodiments of the present disclosure improve thefunctionality of electronic messaging software and systems by generatinganimation in a communication session. In one embodiment, the electronicmessaging system hosts a communication session between two or moreusers. Each of the users can be represented by an avatar which appears achat presence bar of the communication interface when the users arepresent in the communication session. A first user in the communicationsession can cause an animation overlay to be sent to the users in thecommunication session. The animation overlay is then caused to bedisplayed on the communication interfaces of the client devices of theusers in the communication session. The animation overlay is anephemeral animation that includes the avatar associated with the firstuser. The animation overlay can also include an avatar associated withanother user in the communication session. In one embodiment, theanimation overlay can include a three-dimensional animation.

While a group of users can be members of a group communication (e.g.,group chat), a communication session includes the members that arepresent or active in the group communication. The members that areactively participating can be a subset of the members of the groupcommunication or all of the members in the group communication. Themembers that are actively participating can be members that have thecommunication interface displayed on the members' client device. In someembodiments, the animation overlay appears on the client devices of theusers that are present in the communication session. In otherembodiments, the animation overlay can appear on the client devices ofthe all the users in the group communication even if the user is notpresent in the group communication (e.g., group chat) at the time theanimation overlay was generated. In this embodiment, the animationoverlay can appear on the client devices of the absent users at the timethe users are rejoin (or are present) in the group communication (e.g.,when the user opens the group chat on his client device).

In addition to the first animation overlay being displayed on the clientdevices, the system may also cause the client devices to vibrate orgenerate a sound. The vibration or sound generated by the client devicesmay also occur concurrently with the animation of the first user'savatar on the client devices.

Using the animation overlays, the messaging system provides the usersnew way to communicate using the system. Specifically, this animationoverlay is displayed as an additional layer to the communicationinterface and thus, provides a new dimension within the messaging systemthat is private, in real-time, and not traceable. Since thisfunctionality is available to users that are present in thecommunication session, the system is further improved in that it mayincrease the engagement of users with the system as well as increase thelength of time the users maintain presence.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple client devices 102, each ofwhich hosts a number of applications including a messaging clientapplication 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet). As used herein, the term “client device” may referto any machine that interfaces to a communications network (such asnetwork 106) to obtain resources from one or more server systems orother client devices. A client device may be, but is not limited to, amobile phone, desktop computer, laptop, portable digital assistants(PDAs), smart phones, tablets, ultra books, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

In the example shown in FIG. 1, each messaging client application 104 isable to communicate and exchange data with another messaging clientapplication 104 and with the messaging server system 108 via the network106. The data exchanged between messaging client applications 104, andbetween a messaging client application 104 and the messaging serversystem 108, includes functions (e.g., commands to invoke functions) aswell as payload data (e.g., text, audio, video or other multimediadata).

The network 106 may include, or operate in conjunction with, an ad hocnetwork, an intranet, an extranet, a virtual private network (VPN), alocal area network (LAN), a wireless LAN (WLAN), a wide area network(WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), theInternet, a portion of the Internet, a portion of the Public SwitchedTelephone Network (PSTN), a plain old telephone service (POTS) network,a cellular telephone network, a wireless network, a Wi-Fi® network,another type of network, or a combination of two or more such networks.For example, a network or a portion of a network may include a wirelessor cellular network and the coupling may be a Code Division MultipleAccess (CDMA) connection, a Global System for Mobile communications(GSM) connection, or other type of cellular or wireless coupling. Inthis example, the coupling may implement any of a variety of types ofdata transfer technology, such as Single Carrier Radio TransmissionTechnology (1×RTT), Evolution-Data Optimized (EVDO) technology, GeneralPacket Radio Service (GPRS) technology, Enhanced Data rates for GSMEvolution (EDGE) technology, third Generation Partnership Project (3GPP)including 3G, fourth generation wireless (4G) networks, Universal MobileTelecommunications System (UMTS), High Speed Packet Access (HSPA),Worldwide Interoperability for Microwave Access (WiMAX), Long TermEvolution (LTE) standard, others defined by various standard settingorganizations, other long range protocols, or other data transfertechnology.

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality either within the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include, message content, client device information,geolocation information, media annotation and overlays, message contentpersistence conditions, social network information, and live eventinformation, as examples. Data exchanges within the messaging system 100are invoked and controlled through functions available via userinterfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server110, this server receives and transmits message data (e.g., commands andmessage payloads) between the client device 102 and the applicationserver 112. Specifically, the Application Program Interface (API) server110 provides a set of interfaces (e.g., routines and protocols) that canbe called or queried by the messaging client application 104 in order toinvoke functionality of the application server 112. The ApplicationProgram Interface (API) server 110 exposes various functions supportedby the application server 112, including account registration, loginfunctionality, the sending of messages, via the application server 112,from a particular messaging client application 104 to another messagingclient application 104, the sending of media files (e.g., images orvideo) from a messaging client application 104 to the messaging serverapplication 114, and for possible access by another messaging clientapplication 104, the setting of a collection of media data (e.g.,story), the retrieval of a list of friends of a user of a client device102, the retrieval of such collections, the retrieval of messages andcontent, the adding and deletion of friends to a social graph, thelocation of friends within a social graph, opening and application event(e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116 and a social network system 122. The messagingserver application 114 implements a number of message processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia contentincluding images and video clips) included in messages received frommultiple instances of the messaging client application 104. As will bedescribed in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories or galleries). These collections are then made available, by themessaging server application 114, to the messaging client application104. Other processor and memory intensive processing of data may also beperformed server-side by the messaging server application 114, in viewof the hardware requirements for such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 within thedatabase 120. Examples of functions and services supported by the socialnetwork system 122 include the identification of other users of themessaging system 100 with which a particular user has relationships oris “following”, and also the identification of other entities andinterests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

Some embodiments may include one or more wearable devices, such as apendant with an integrated camera that is integrated with, incommunication with, or coupled to, a client device 102. Any desiredwearable device may be used in conjunction with the embodiments of thepresent disclosure, such as a watch, eyeglasses, goggles, a headset, awristband, earbuds, clothing (such as a hat or jacket with integratedelectronics), a clip-on electronic device, and/or any other wearabledevices.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to exemplary embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a story), selectively display and enableaccess to messages and associated content via the messaging clientapplication 104.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery” or an “event story.” Such a collection may be made availablefor a specified time period, such as the duration of an event to whichthe content relates. For example, content relating to a music concertmay be made available as a “story” for the duration of that musicconcert. The collection management system 204 may also be responsiblefor publishing an icon that provides notification of the existence of aparticular collection to the user interface of the messaging clientapplication 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion of usergenerated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay (e.g., a filter) to the messagingclient application 104 based on a geolocation of the client device 102.In another example, the annotation system 206 operatively supplies amedia overlay to the messaging client application 104 based on otherinformation, such as, social network information of the user of theclient device 102. A media overlay may include audio and visual contentand visual effects. Examples of audio and visual content includepictures, texts, logos, animations, and sound effects. An example of avisual effect includes color overlaying. The audio and visual content orthe visual effects can be applied to a media content item (e.g., aphoto) at the client device 102. For example, the media overlayincluding text that can be overlaid on top of a photograph generatedtaken by the client device 102. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice beach), aname of a live event, or a name of a merchant overlay (e.g., BeachCoffee House). In another example, the annotation system 206 uses thegeolocation of the client device 102 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 120 andaccessed through the database server 118.

In one exemplary embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another exemplary embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time

FIG. 3 is a schematic diagram 300 illustrating data 300 which may bestored in the database 120 of the messaging server system 108, accordingto certain exemplary embodiments. While the content of the database 120is shown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events etc. Regardless of type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of variestypes, including a user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filers includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filer is a data filer, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102 or thecurrent time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 302). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client application 104 may include an icon that is userselectable to enable a sending user to add specific content to his orher personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automaticallyor using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users, whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

Embodiments of the present disclosure may generate and presentcustomized images for use within electronic messages such as SMS or MMStexts and emails. The customized images may also be utilized inconjunction with the stories, filters, and ephemeral messagingfunctionality discussed herein.

FIG. 4 are exemplary flow diagrams of processes according to variousaspects of the disclosure. Although the flowcharts may describe theoperations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations may be re-arranged. A process is terminated when itsoperations are completed. A process may correspond to a method, aprocedure, etc. The steps of methods may be performed in whole or inpart, may be performed in conjunction with some or all of the steps inother methods, and may be performed by any number of different systems,such as the systems described in FIG. 1 and/or FIG. 7.

FIG. 4 depicts an exemplary process of generating private notificationsbetween users in a communication session according to various aspects ofthe present disclosure. In this example, method 400 starts, at operation410, with an application server of the messaging server system causing acommunication interface for a communication session to be displayed atplurality of client devices. The communication session can be betweentwo or more client devices. For example, FIGS. 5A-5B illustrate examplesof the communication interface 500 being displayed at a first clientdevice. As shown in FIGS. 5A-5B, the communication interface 500includes a communication window 503 that displays the electroniccommunications (e.g., chat, text, images, animations) that were sentfrom users in the group chat (e.g., group communication).

While a group of users can be members of a group communication (e.g.,group chat), a communication session includes the members that areactively participating in the group communication. The members that areactively participating can be a subset of the members of the groupcommunication or all of the members in the group communication. Forexample, the members that are considered to be actively participating(or present) are the members have the communication interface displayedon the members' client device.

As shown in FIGS. 5A-5B, the communication interface 500 includes a chatpresence bar 501 that includes presence indicators 502_1 to 502_n (n>1)associated with users of the client devices, respectively. In oneembodiment, the presence indicators include the avatars of the users inthe communication session. When a user is present (e.g., in an activestate) in the communication session, an avatar associated with the usermay be displayed in the chat presence bar 501 as a presence indicatorfor the user. In this example, the display of at least a portion of theuser's avatar (e.g., a crouched avatar, a standing avatar, etc.) in thechat presence bar is the presence indicator is in an active state.Specifically, in a communication session that includes a first user of afirst client device and a second user of a second client device, whenthe first user and the second user are present in the communicationsession, the first user's presence indicator (e.g., first avatar) andthe second user's presence indicator (e.g., second avatar) are includedin the chat presence bar of the communication interface displayed on thefirst client device and the second client device. For example, in FIGS.5A-5B, the chat presence bar 501 in the communication interface 500 ofthe first client device includes two avatars 502_1, 502_2 whichindicates that the two users associated with the two avatars 502_1,502_2 are present or active in the communication session. In oneembodiment, the first avatar 5021 is associated with the first user ofthe first client device.

In one embodiment, the application server can receive user identifiersassociated with the users in the communication session and avatarcharacteristics associated with the user identifiers, respectively. Insome embodiments, the user identifier may be received from an inputwithin an electronic message from a client device 102 (e.g., the user'sclient device 102). For example, the user could input, via the userinterface of the user's computing device, his or her name to generatethe user's own customized avatar. Additionally or alternatively, theuser identifier may be received based on information stored within theuser's computing device. Any such identifier may be used, such as theuser's full name or a username associated with the user. The useridentifier may also be an identifier associated with the user'scomputing device, such as a Unique Device Identifier (UDID) orIdentifier for Advertising (IDFA).

As used herein, an “avatar” of a user is any visual representation ofuser. The avatar of a user or individual may be any image resembling orotherwise associated with the user or individual. The avatar of a usermay be based on characteristics derived from images of the user inconjunction with the avatar characteristics identified from the user'srelationships with other users. Alternatively or additionally, the usermay select and customize characteristics of the user's avatar via theuser's computing device (i.e., customized avatar characteristics). Suchcustomized avatar characteristics may include, for example, the user'sbodily features (e.g., muscular, thin, etc.), facial features, clothingand accessories, text displayed in conjunction with the avatar, andimages displayed in conjunction with the avatar. The avatarcharacteristics may be received or retrieved from a variety of sources,such as the local memory of a client device 102 as well as from othersystems and devices, such as a database or server.

Referring back to FIG. 4, at operation 420, the application serverreceives an animation sending request from the first client device. Inone embodiment, the animation sending request is received when the firstclient device detects a selection of the presence indicator associatedwith the user of the first client device. For example, the first usercan select his own avatar (e.g., the first presence indicator 502_1)from the chat presence bar 501 in FIGS. 5A-5B. In one embodiment, thepresence indicators 502_1-502_n are selectable user interface items.When the first user can select his own (first) avatar 502_1, the displayof the first avatar 502_1 that appears crouched behind the chat presencebar 501 in FIG. 5A can change to appear to rise from behind the chatpresence bar 501.

In another embodiment, the animation sending request is received whenthe first client device detects a selection of the presence indicatorassociated with the user of the second client device that is present inthe communication session. For example, the first user can select thesecond presence indicator 502_2 (e.g., second avatar) from the chatpresence bar 501 in FIGS. 5A-5B. When the first user can select thesecond presence indicator 502_2, the display of the second avatar 502_2that appears crouched behind the chat presence bar 501 in FIG. 5A canchange to appear to rise from behind the chat presence bar 501 as shownin FIG. 5B.

In another embodiment, the animation sending request is received whenthe first client device detects a selection of two or more presenceindicators associated with users of the client devices that is presentin the communication session. For example, within a predetermined periodof time, the first user can select the two or more presence indicators501_2-501_n in the chat presence bar 501.

In another embodiment, the animation sending request is received whenthe first client device detects a selection associated with a user thatis a member of the group communication but that is not currently activein the communication session. In one embodiment, the chat presence barincludes a presence indicator in an inactive state which indicates thatthe user is not currently active or present (e.g., grayed out name tab,grayed out avatar, etc.).

In one embodiment, the animation sending request is received when thefirst client device detects a selection associated with an icon 505 thatis included in the communication interface 500 in FIGS. 5A-5B. In oneembodiment the icon 505 can be a selectable interface item that isassociated with additional options of content items that can be sent(e.g., animation overlays, stickers, Graphics Interchange Format (gifs),songs, etc.).

At operation 430, the application server causes an animation sendinginterface to be displayed in the communication interface of the firstclient device. For example, when the first user selects the firstpresence indicator 502_1 (e.g., second avatar) from the communicationinterface 500 in FIGS. 5A-5B, the animation sending interface 510 inFIG. 5C is caused to be displayed in the communication interface 500 ofthe first client device. The animation sending interface 510 appear overthe communication interface 500 in FIGS. 5A-5B. In some examples, theanimation sending interface 510 is a card that slides upwards from thebottom of the communication interface 500 in FIGS. 5A-5B. As shown inFIG. 5C, the animation sending interface 510 includes animation overlayicons 511_1 to 511_m (m>1). Each of the animation overlay icons 511_1 to511_m includes the first avatar that is associated with the first user.The animation overlay icons 511_1 to 511_m are selectable user interfaceitems that correspond to animation overlays featuring the first avatar.

In another example, when the first user selects the second presenceindicator 502_2 (e.g., second avatar) from the communication interface500 in FIGS. 5A-5B, the animation sending interface 520 in FIG. 5D iscaused to be displayed in the communication interface 500 of the firstclient device. The animation sending interface 520 appear over thecommunication interface 500 in FIGS. 5A-5B. In some examples, theanimation sending interface 520 is a card that slides upwards from thebottom of the communication interface 500 in FIGS. 5A-5B. As shown inFIG. 5D, the animation sending interface 520 includes animation overlayicons 521_1 to 521_p (p>1). Each of the animation overlay icons 521_1 to521_p includes the first avatar that is associated with the first userand the second avatar that is associated with the second user. Theanimation overlay icons 521_1 to 521_p are selectable user interfaceitems that correspond to animation overlays featuring the first avatarand the second avatar.

In one embodiment, when the first client device detects a selection oftwo or more presence indicators associated with users of the clientdevices that is present in the communication session, the animationsending interface includes animation overlay icons that comprise theavatars of the users corresponding to the selection of two or morepresence indicators. Similarly, when the first client device detects aselection associated with a user that is a member of the groupcommunication but that is not currently active in the communicationsession. The animation sending interface includes animation overlayicons that comprise an avatar of the selected inactive user.

In one embodiment, when the first user selects the icon 505 from thecommunication interface 500 in FIGS. 5A-5B, the animation sendinginterface 530 in FIG. 5E is caused to be displayed in the communicationinterface 500 of the first client device. The animation sendinginterface 530 appear over the communication interface 500 in FIGS.5A-5B. In some examples, the animation sending interface 530 is a cardthat slides upwards from the bottom of the communication interface 500in FIGS. 5A-5B. As shown in FIG. 5E, the animation sending interface 530includes animation overlay icons 511_1-511_m. Each of the animationoverlay icons 511_1-511_m includes the first avatar that is associatedwith the first user. In one embodiment, the animation sending interface530 can further include the animation overlay icons 521_1-521_p includesthe first avatar that is associated with the first user and the secondavatar that is associated with the second user.

At operation 440, the application server receives from the first clientdevice a selection of a first animation overlay icon included in theplurality of animation overlays icons. For example, the first animationoverlay icon 510_1 can be selected from the animation overlay icons510_1-510_m in FIG. 5C which includes the first avatar.

At operation 450, the application server causes a first animationoverlay corresponding to the first animation overlay icon to bedisplayed as an overlay on the communication interface of each of theplurality of client devices. In one embodiment, the application servertransmits the first animation overlay to be displayed on thecommunication interface of each of the client devices. For example, thefirst animation overlay that corresponds to the first animation overlayicon 511_1 is an animation that includes the first avatar playing theguitar. When the first animation overlay is caused to be displayed onthe client devices of the users in the communication session, the firstanimation overlay can appear as an overlay which is a layer above thecommunication window 503 (e.g., the portion of the communicationinterface 500 where the text or image messages are being displayed). Inone embodiment, the animation overlay is caused to be displayedephemerally for a predetermined period of time. For example, the firstanimation overlay can be displayed ephemerally for the duration of theanimation. The first animation overlay can be an animation that includesthe first avatar appearing to be animated and playing the guitar. Insome embodiments, in addition to the first animation overlay beingdisplayed, the application server can also cause the client devices inthe communication session to vibrate or generate a sound. For example,in conjunction with the first animation overlay being displayed on theplurality of client devices, the client devices can be caused to vibrateor generate guitar sounds or a song. In one embodiment, the firstanimation overlay is a three-dimensional animation.

In another example, the first animation overlay that corresponds to thefirst animation overlay icon 521_1 is an animation that includes thefirst avatar and the second avatar giving each other a high five.Similarly, the first animation overlay can be an animation that includesthe first avatar and the second avatar performing an animation whereinthey are giving each other a high five. In FIG. 5F, an example of afirst animation overlay 540 that is displayed as an overlay on thecommunication interface 500 of each of the client devices is shown. Thefirst animation overlay 540 can include the first avatar and a secondavatar performing an animation. Specifically, the first animationoverlay 540 corresponds to the first animation overlay icon 520_1 suchthat, as shown in FIG. 5F, the first and second avatars are performingan animation in which they are giving each other a high-five.

In one embodiment, the first animation overlay 540 appears above thepresence chat bar 510. The avatars in the first animation overlay 540can appear to use the presence chat bar 510 as a floor to perform theiranimation thereon. Once the animation is complete, the first animationoverlay 540 disappears to reveal the communication interface 500 withthe communication window 503. In one embodiment, once completed, thefirst animation overlay 540 leaves no trace and cannot be replayed. Inanother embodiment, the first animation overlay 540 may indicate in thecommunication window 503 that the first user sent the first overlay.

In some embodiments, the first animation overlay appears on the clientdevices of the users that are present in the communication session. Inother embodiments, the animation overlay can appear on the clientdevices of the all the users in the group communication (e.g., groupchat) even if the user is not active or present in the communicationsession at the time the animation overlay was generated. In thisembodiment, the animation overlay can appear on the client devices ofthe absent users at the time the users become active in the groupcommunication (e.g., when the user opens the group chat on his clientdevice). The application server can cause the client devices of theusers that are not present in the communication session to generate anotification indicating that the first user has sent an animationoverlay to the group. The notification can appear as a push notificationon the client devices.

In one embodiment, rather than sending the first animation overlay tothe client devices of the users in the communication session or thegroup communication (e.g., group chat), the first user can select theone or more users in the group communication to receive the firstanimation overlay.

FIG. 6 is a block diagram illustrating an example software architecture606, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 6 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 606 may execute on hardwaresuch as machine 700 of FIG. 7 that includes, among other things,processors 704, memory 714, and I/O components 718. A representativehardware layer 652 is illustrated and can represent, for example, themachine 700 of FIG. 7. The representative hardware layer 652 includes aprocessing unit 654 having associated executable instructions 604.Executable instructions 604 represent the executable instructions of thesoftware architecture 606, including implementation of the methods,components and so forth described herein. The hardware layer 652 alsoincludes memory and/or storage modules memory/storage 656, which alsohave executable instructions 604. The hardware layer 652 may alsocomprise other hardware 658.

As used herein, the term “component” may refer to a device, physicalentity or logic having boundaries defined by function or subroutinecalls, branch points, application program interfaces (APIs), and/orother technologies that provide for the partitioning or modularizationof particular processing or control functions. Components may becombined via their interfaces with other components to carry out amachine process. A component may be a packaged functional hardware unitdesigned for use with other components and a part of a program thatusually performs a particular function of related functions.

Components may constitute either software components (e.g., codeembodied on a machine-readable medium) or hardware components. A“hardware component” is a tangible unit capable of performing certainoperations and may be configured or arranged in a certain physicalmanner. In various exemplary embodiments, one or more computer systems(e.g., a standalone computer system, a client computer system, or aserver computer system) or one or more hardware components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) as a hardwarecomponent that operates to perform certain operations as describedherein. A hardware component may also be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware component may include dedicated circuitry or logic that ispermanently configured to perform certain operations.

A hardware component may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware component may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

A processor may be, or in include, any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands”, “op codes”, “machine code”, etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an Application SpecificIntegrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC)or any combination thereof. A processor may further be a multi-coreprocessor having two or more independent processors (sometimes referredto as “cores”) that may execute instructions contemporaneously.

Accordingly, the phrase “hardware component” (or “hardware-implementedcomponent”) should be understood to encompass a tangible entity, be thatan entity that is physically constructed, permanently configured (e.g.,hardwired), or temporarily configured (e.g., programmed) to operate in acertain manner or to perform certain operations described herein.Considering embodiments in which hardware components are temporarilyconfigured (e.g., programmed), each of the hardware components need notbe configured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processorconfigured by software to become a special-purpose processor, thegeneral-purpose processor may be configured as respectively differentspecial-purpose processors (e.g., comprising different hardwarecomponents) at different times. Software accordingly configures aparticular processor or processors, for example, to constitute aparticular hardware component at one instance of time and to constitutea different hardware component at a different instance of time. Hardwarecomponents can provide information to, and receive information from,other hardware components. Accordingly, the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between such hardwarecomponents may be achieved, for example, through the storage andretrieval of information in memory structures to which the multiplehardware components have access.

For example, one hardware component may perform an operation and storethe output of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components.

Moreover, the one or more processors may also operate to supportperformance of the relevant operations in a “cloud computing”environment or as a “software as a service” (SaaS). For example, atleast some of the operations may be performed by a group of computers(as examples of machines including processors), with these operationsbeing accessible via a network (e.g., the Internet) and via one or moreappropriate interfaces (e.g., an Application Program Interface (API)).The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some exemplary embodiments, theprocessors or processor-implemented components may be located in asingle geographic location (e.g., within a home environment, an officeenvironment, or a server farm). In other exemplary embodiments, theprocessors or processor-implemented components may be distributed acrossa number of geographic locations.

In the exemplary architecture of FIG. 6, the software architecture 606may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 606 mayinclude layers such as an operating system 602, libraries 620,applications 616 and a presentation layer 614. Operationally, theapplications 616 and/or other components within the layers may invokeapplication programming interface (API) API calls 608 through thesoftware stack and receive messages 612 in response to the API calls608. The layers illustrated are representative in nature and not allsoftware architectures have all layers. For example, some mobile orspecial purpose operating systems may not provide aframeworks/middleware 618, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 602 may manage hardware resources and providecommon services. The operating system 602 may include, for example, akernel 622, services 624 and drivers 626. The kernel 622 may act as anabstraction layer between the hardware and the other software layers.For example, the kernel 622 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 624 may provideother common services for the other software layers. The drivers 626 areresponsible for controlling or interfacing with the underlying hardware.For instance, the drivers 626 include display drivers, camera drivers,Bluetooth® drivers, flash memory drivers, serial communication drivers(e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audiodrivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 620 provide a common infrastructure that is used by theapplications 616 and/or other components and/or layers. The libraries620 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 602 functionality (e.g., kernel 622,services 624 and/or drivers 626). The libraries 620 may include systemlibraries 644 (e.g., C standard library) that may provide functions suchas memory allocation functions, string manipulation functions,mathematical functions, and the like. In addition, the libraries 620 mayinclude API libraries 646 such as media libraries (e.g., libraries tosupport presentation and manipulation of various media format such asMPEG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., anOpenGL framework that may be used to render 2D and 3D in a graphiccontent on a display), database libraries (e.g., SQLite that may providevarious relational database functions), web libraries (e.g., WebKit thatmay provide web browsing functionality), and the like. The libraries 620may also include a wide variety of other libraries 648 to provide manyother APIs to the applications 616 and other softwarecomponents/modules.

The frameworks/middleware 618 (also sometimes referred to as middleware)provide a higher-level common infrastructure that may be used by theapplications 616 and/or other software components/modules. For example,the frameworks/middleware 618 may provide various graphic user interface(GUI) functions, high-level resource management, high-level locationservices, and so forth. The frameworks/middleware 618 may provide abroad spectrum of other APIs that may be utilized by the applications616 and/or other software components/modules, some of which may bespecific to a particular operating system 602 or platform.

The applications 616 include built-in applications 638 and/orthird-party applications 640. Examples of representative built-inapplications 638 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 640 may include anapplication developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 640 may invoke the API calls 608 provided bythe mobile operating system (such as operating system 602) to facilitatefunctionality described herein.

The applications 616 may use built in operating system functions (e.g.,kernel 622, services 624 and/or drivers 626), libraries 620, andframeworks/middleware 618 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 614. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 7 is a block diagram illustrating components (also referred toherein as “modules”) of a machine 700, according to some exemplaryembodiments, able to read instructions from a machine-readable medium(e.g., a machine-readable storage medium) and perform any one or more ofthe methodologies discussed herein. Specifically, FIG. 7 shows adiagrammatic representation of the machine 700 in the example form of acomputer system, within which instructions 710 (e.g., software, aprogram, an application, an applet, an app, or other executable code)for causing the machine 700 to perform any one or more of themethodologies discussed herein may be executed. As such, theinstructions 710 may be used to implement modules or componentsdescribed herein. The instructions 710 transform the general,non-programmed machine 700 into a particular machine 700 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 700 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 700 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 700 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 710, sequentially or otherwise, that specify actions to betaken by machine 700. Further, while only a single machine 700 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 710 to perform any one or more of the methodologiesdiscussed herein.

The machine 700 may include processors 704, memory memory/storage 706,and I/O components 718, which may be configured to communicate with eachother such as via a bus 702. The memory/storage 706 may include a memory714, such as a main memory, or other memory storage, and a storage unit716, both accessible to the processors 704 such as via the bus 702. Thestorage unit 716 and memory 714 store the instructions 710 embodying anyone or more of the methodologies or functions described herein. Theinstructions 710 may also reside, completely or partially, within thememory 714, within the storage unit 716, within at least one of theprocessors 704 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine700. Accordingly, the memory 714, the storage unit 716, and the memoryof processors 704 are examples of machine-readable media.

As used herein, the term “machine-readable medium,” “computer-readablemedium,” or the like may refer to any component, device or othertangible media able to store instructions and data temporarily orpermanently. Examples of such media may include, but is not limited to,random-access memory (RAM), read-only memory (ROM), buffer memory, flashmemory, optical media, magnetic media, cache memory, other types ofstorage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/orany suitable combination thereof. The term “machine-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” may alsobe taken to include any medium, or combination of multiple media, thatis capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” may refer to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

The I/O components 718 may include a wide variety of components toprovide a user interface for receiving input, providing output,producing output, transmitting information, exchanging information,capturing measurements, and so on. The specific U/O components 718 thatare included in the user interface of a particular machine 700 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 718 may include many other components that are not shown inFIG. 7. The I/O components 718 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various exemplary embodiments, the I/O components718 may include output components 726 and input components 728. Theoutput components 726 may include visual components (e.g., a displaysuch as a plasma display panel (PDP), a light emitting diode (LED)display, a liquid crystal display (LCD), a projector, or a cathode raytube (CRT)), acoustic components (e.g., speakers), haptic components(e.g., a vibratory motor, resistance mechanisms), other signalgenerators, and so forth. The input components 728 may includealphanumeric input components (e.g., a keyboard, a touch screenconfigured to receive alphanumeric input, a photo-optical keyboard, orother alphanumeric input components), point based input components(e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, orother pointing instrument), tactile input components (e.g., a physicalbutton, a touch screen that provides location and/or force of touches ortouch gestures, or other tactile input components), audio inputcomponents (e.g., a microphone), and the like. The input components 728may also include one or more image-capturing devices, such as a digitalcamera for generating digital images and/or video.

In further exemplary embodiments, the I/O components 718 may includebiometric components 730, motion components 734, environmentalenvironment components 736, or position components 738, as well as awide array of other components. One or more of such components (orportions thereof) may collectively be referred to herein as a “sensorcomponent” or “sensor” for collecting various data related to themachine 700, the environment of the machine 700, a user of the machine700, or a combinations thereof.

For example, the biometric components 730 may include components todetect expressions (e.g., hand expressions, facial expressions, vocalexpressions, body gestures, or eye tracking), measure biosignals (e.g.,blood pressure, heart rate, body temperature, perspiration, or brainwaves), identify a person (e.g., voice identification, retinalidentification, facial identification, fingerprint identification, orelectroencephalogram based identification), and the like. The motioncomponents 734 may include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope), and so forth. The environment components736 may include, for example, illumination sensor components (e.g.,photometer), temperature sensor components (e.g., one or morethermometer that detect ambient temperature), humidity sensorcomponents, pressure sensor components (e.g., barometer), acousticsensor components (e.g., one or more microphones that detect backgroundnoise), proximity sensor components (e.g., infrared sensors that detectnearby objects), gas sensors (e.g., gas detection sensors to detectionconcentrations of hazardous gases for safety or to measure pollutants inthe atmosphere), or other components that may provide indications,measurements, or signals corresponding to a surrounding physicalenvironment. The position components 738 may include location sensorcomponents (e.g., a Global Position system (GPS) receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like. For example, thelocation sensor component may provide location information associatedwith the system 700, such as the system's 700 GPS coordinates and/orinformation regarding a location the system 700 is at currently (e.g.,the name of a restaurant or other business).

Communication may be implemented using a wide variety of technologies.The I/O components 718 may include communication components 740 operableto couple the machine 700 to a network 732 or devices 720 via coupling722 and coupling 724 respectively. For example, the communicationcomponents 740 may include a network interface component or othersuitable device to interface with the network 732. In further examples,communication components 740 may include wired communication components,wireless communication components, cellular communication components,Near Field Communication (NFC) components, Bluetooth® components (e.g.,Bluetooth® Low Energy), Wi-Fi® components, and other communicationcomponents to provide communication via other modalities. The devices720 may be another machine or any of a wide variety of peripheraldevices (e.g., a peripheral device coupled via a Universal Serial Bus(USB)).

Moreover, the communication components 740 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 740 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components740, such as, location via Internet Protocol (IP) geo-location, locationvia Wi-Fi® signal triangulation, location via detecting a NFC beaconsignal that may indicate a particular location, and so forth.

Where a phrase similar to “at least one of A, B, or C,” “at least one ofA, B, and C,” “one or more A, B, or C,” or “one or more of A, B, and C”is used, it is intended that the phrase be interpreted to mean that Aalone may be present in an embodiment, B alone may be present in anembodiment, C alone may be present in an embodiment, or that anycombination of the elements A, B and C may be present in a singleembodiment; for example, A and B, A and C, B and C, or A and B and C.

Changes and modifications may be made to the disclosed embodimentswithout departing from the scope of the present disclosure. These andother changes or modifications are intended to be included within thescope of the present disclosure, as expressed in the following claims.

1. A system comprising: a processor; and a memory component having instructions stored thereon, when executed by the processor, causes the system to perform operations comprising: causing a communication interface for a communication session to be displayed at a plurality of client devices including a first client device that is associated with a first user and a second client device that is associated with a second user, the first user being associated with a first avatar and the second user being associated with a second avatar; causing an animation sending interface to be displayed in the communication interface of the first client device, the animation sending interface comprising a plurality of animation overlays icons, the animation overlays icons comprising the first avatar and the second avatar performing a plurality of actions, wherein the first avatar and the second avatar in each of the animation overlay icons includes a body and a head of the first avatar having avatar characteristics associated with the first user and of the second avatar having avatar characteristics associated with the second user; receiving from the first client device a selection of a first animation overlay icon of the plurality of animation overlays icons, the first animation overlay icon comprising the first avatar and the second avatar performing a first action of the plurality of actions; and causing a first animation overlay corresponding to the first animation overlay icon to be displayed as an overlay on the communication interface of each of the plurality of client devices, the first animation overlay being an animation that includes the first avatar and the second avatar performing the first action, wherein the overlay is displayed as a layer above the communication interface.
 2. The system of claim 1, wherein the communication interface includes a chat presence bar that includes a plurality of presence indicators associated with the users of the client devices.
 3. The system of claim 2, wherein the chat presence bar displayed on the first client device comprises the presence indicator associated with the first user in an active state, wherein the presence indicator associated with the first user in the active state includes at least a portion of the first avatar.
 4. The system of claim 3, wherein, when the first user and the second user are present in the communication session, the chat presence bar displayed on the first client device and the second client device comprises the presence indicator associated with the first user in the active state and the presence indicator associated with the second user in the active state.
 5. The system of claim 4, wherein the system causes the animation sending interface to be displayed in response to the first client device detecting activation of the presence indicator associated with the first user in the active state.
 6. The system of claim 4, wherein the system causes the animation sending interface to be displayed in response the first client device detecting activation of the presence indicator associated with the second user in the active state.
 7. The system of claim 2, wherein the first animation overlay is caused to be displayed above the chat presence bar.
 8. The system of claim 1, wherein causing the first animation overlay to be displayed as the overlay on the communication interface of each of the plurality of client devices comprises: causing the first animation overlay to be displayed for a predetermined period of time.
 9. The system of claim 1, wherein the first animation overlay is a three-dimensional animation.
 10. The system of claim 1, wherein causing the first animation overlay to be displayed as the overlay on the communication interface of each of the plurality of client devices comprises: causing the first animation overlay to be displayed on each of the plurality of client devices associated with users that are present in the communication session.
 11. A method comprising: causing, by a processor, a communication interface for a communication session to be displayed at a plurality of client devices including a first client device that is associated with a first user and a second client device that is associated with a second user, the first user being associated with a first avatar and the second user being associated with a second avatar causing an animation sending interface to be displayed in the communication interface of the first client device, the animation sending interface comprising a plurality of animation overlays icons, the animation overlays icons comprising the first avatar and the second avatar performing a plurality of actions, wherein the first avatar and the second avatar in each of the animation overlay icons includes a body and a head of the first avatar having avatar characteristics associated with the first user and of the second avatar having avatar characteristics associated with the second user; receiving from the first client device a selection of a first animation overlay icon of the plurality of animation overlays icons, the first animation overlay icon comprising the first avatar and the second avatar performing a first action of the plurality of actions; and causing a first animation overlay corresponding to the first animation overlay icon to be displayed on the communication interface of each of the plurality of client devices, the first animation overlay being an animation that includes the first avatar and the second avatar performing the first action, wherein the overlay is displayed as a layer above the communication interface.
 12. The method of claim 11, wherein the communication interface includes a chat presence bar that includes a plurality of presence indicators associated with users of the client devices, respectively.
 13. The method of claim 12, wherein the chat presence bar displayed on the first client device comprises the presence indicator associated with the first user in an active state, wherein the presence indicator associated with the first user in the active state includes at least a portion of the first avatar.
 14. The method of claim 13, wherein, when the first user and the second user are present in the communication session, the chat presence bar displayed on the first client device and the second client device comprises the presence indicator associated with the first user in the active state and the presence indicator associated with the second user in the active state.
 15. The method of claim 14, wherein the animation sending interface is caused to be displayed in response to the first client device detecting activation of the presence indicator associated with the first user in the active state.
 16. The method of claim 14, wherein the animation sending interface is caused to be displayed in response to the first client device detecting activation of the presence indicator associated with the second user in the active state.
 17. The method of claim 12, wherein the first animation overlay is caused to be displayed above the chat presence bar.
 18. The method of claim 11, wherein causing the first animation overlay to be displayed as the overlay on the communication interface of each of the plurality of client devices comprises: causing the first animation overlay to be displayed for a predetermined period of time.
 19. The method of claim 11, wherein the first animation overlay is a three-dimensional animation.
 20. The method of claim 11, wherein causing the first animation overlay to be displayed as the overlay on the communication interface of each of the plurality of client devices comprises: causing the first animation overlay to be displayed on each of the plurality of client devices associated with users that are present in the communication session.
 21. The method of claim 11, wherein causing the first animation overlay to be displayed further comprises: causing the plurality of client devices to vibrate or generate a sound.
 22. A non-transitory computer-readable storage medium having stored thereon, instructions when executed by a processor, causes the processor to perform operations comprising: causing a communication interface for a communication session to be displayed at a plurality of client devices including a first client device that is associated with a first user and a second client device that is associated with a second user, the first user being associated with a first avatar and the second user being associated with a second avatar causing an animation sending interface to be displayed in the communication interface of the first client device, the animation sending interface comprising a plurality of animation overlays icons, the animation overlays icons comprising the first avatar and the second avatar performing a plurality of actions, wherein the first avatar and the second avatar in each of the animation overlay icons includes a body and a head of the first avatar having avatar characteristics associated with the first user and of the second avatar having avatar characteristics associated with the second user; receiving from the first client device a selection of a first animation overlay icon of the plurality of animation overlays icons, the first animation overlay icon comprising the first avatar and the second avatar performing a first action of the plurality of actions; and causing a first animation overlay corresponding to the first animation overlay icon to be displayed on the communication interface of each of the plurality of client devices, the first animation overlay being an animation that includes the first avatar and the second avatar performing the first action, wherein the overlay is displayed as a layer above the communication interface. 